I have a fully patched Exchange 2013 server and the latest Thunderbird IMAP-client.

When the user tries to open some subfolders under inbox he gets an error "The current operation on 'subfolder' did not succeed. The mail server for account user@Exchange responed: Server Unavailbale. 15."

Some subfolders work though and subfolders under the subfolder that cant be opened works.

I found this post but no answer to what the user changed to make it work:

https://social.technet.microsoft.com/Forums/office/en-US/2508f50f-6b28-4961-8e6c-5425914d4caa/no-server-unavailable-15-on-exchange-2013?forum=exchangesvrclients

The folder is visible and readable from other clients like Outlook and webmail.

• Edited by Harmankardon Monday, June 15, 2015 10:12 AM

Found a workaround for the problem for one user

If the user copied the mail (via another client or webmail) to another folder and then removed the old folder. Recreated it and then moved the mail back he could see the mail in the folder again.

• Marked as answer by Harmankardon Monday, June 15, 2015 10:15 AM
• Unmarked as answer by Harmankardon Thursday, June 18, 2015 10:34 AM
• Edited by Harmankardon Thursday, June 18, 2015 10:35 AM

Hi!

The problem is not isolated to Outlook. I only used Outlook to see how it behaved. The crucial issue is with Thunderbird as the post says. But every IMAP client I connect gets the same issues. I have only around 5 IMAP-users migrated to 2013 right know (3 of them is having problems) but there will be more in a short period of time and I dont want all of them to have the same problem.

And it is not all folders it is just some folders that give the error (for example "subfolder" in the post above).

So IMAP is working as far as Exchange is concerned but the clients does not seem to like it.

Hi,

How about OWA or configure Outlook with Outlook Anywhere?
Also, run Get-MailboxFolderPermission Identity alias:\ | FL Identity,FolderName,User,AccessRights to ensure the permission configuration after migrate to Exchange 2013.

Besides, please post more details about your migration method for further troubleshooting.

It is not an option for those users to run Outlook since they run a Linuxsystem. And pointing them towards webmail wont be popular. They want their client.

The permissions seems to be right. At least there are no difference between a user that has a folder that cant be opened and a user that works with all folders.

We have migrated from a 2007 environment to 2013. We are still in coexistence. Users who has their mail in 2007 does not have this problem. It is only users in 2013. At first we had the error referenced in CU9:

https://support.microsoft.com/en-us/kb/3064393

But that was fixed with that patch.

The problem seems to be with the configuration of the folers since I can fix the problem with a subfolder by creating a new folder and moving to mail to that folder. Then I can read the mail again. But that is not an option when it comes to the Inbox since I cant create a new inbox and remove the old one.

Hi,

Basic on your post, I want to double ensure the result for Outlook client.

If it works in Outlook, it might be caused by the software conflict. Sorry for any inconvenience.

For Thunderbird client, try: Go to Tools/Options/Advanced/Config Editor: Set boolean mail.check_all_imap_folders_for_new to

I can access the folder via Outlook connected via MAPI. But via IMAP I get the error I posted above:

"If I connect Outlook via IMAP to the same account I get another error:

Error synchronizing folder
[8004DF03-0-0-560]

And  the folder shows up empty"

All other IMAP-clients give "server unavailable 15" when trying to access the folder.

So the problem is not related to the client. It is serverrelated. Something is wrong with the folder on the account.

I tried to change the mail.check_all_imap... to true. It is by the way replaced by:

mail.server.default.check_all_folders_for_new

But it made no change.

Hi,

Thank you for your post.

This is a quick note to let you know that we are performing research on this issue.

Thanks for the update.

I have done some additional testing and I can tell you that if I export the broken mailbox to a pst-file and then import that to a another user or to subfolders in the same mailbox all mailfolders vill be readable again. So the the error is hidden somewhere in the users mailbox.

Import and export will though not help the users that have a broken inbox (subfolders are readeable though). The only fix I found there is disabling the mailbox and then enabling it again and reimport all the mail to that user. But that is not a thing you want to do for every failed mailbox.

Hi,

Sorry for delay.

Through disscussion, this issue might be caused by corrupted mailbox.
We recommend move one mailbox to other database for test first, or use New-MailboxRepairRequest to repair mailbox.

If the issue persists, please help to collect protocol log for further troubleshooting.

Hi!

The mailborepairrequest came up with nothing. What protocollogs would you like to see?

If I use the mapitool I can see two things that differs on working folders and non working folders.

Number one: The working folders does not have a creator_sid. It says no domain and no name.

Also this line does not show up on a working folder.

 

• Edited by Harmankardon Monday, August 10, 2015 8:48 AM

Hi!

The mailborepairrequest came up with nothing. What protocollogs would you like to see?

If I use the mapitool I can see two things that differs on working folders and non working folders.

Number one: The working folders does not have a creator_sid. It says no domain and no name.

Also this line does not show up on a working folder.

 

• Edited by Harmankardon 22 hours 39 minutes ago

It seems like CU9 fixed the problem at least for one user.

• Marked as answer by Harmankardon 15 minutes ago

It seems like CU9 fixed the problem at least for one user.

• Marked as answer by Harmankardon Wednesday, August 12, 2015 7:10 AM